Skip to content

Retry Android emulator with software GPU rendering - #12

Draft
krystofwoldrich wants to merge 10 commits into
mainfrom
codex/software-gpu-fallback
Draft

krystofwoldrich wants to merge 10 commits into
mainfrom
codex/software-gpu-fallback

Conversation

@krystofwoldrich

Copy link
Copy Markdown
Collaborator

Summary

  • monitor Android Emulator stderr while starting with -gpu host
  • detect the hardware-rendering-unavailable error and retry once with -gpu software
  • keep the retry silent except for the existing expo-device-hub:android-utils debug namespace
  • make the returned process lifecycle and diagnostic command follow the software-rendered retry
  • document the fallback behavior

Why

Headless workers without a usable hardware GPU fail when the emulator is forced to use -gpu host. The launcher previously discarded stderr, so it could neither identify that specific failure nor recover from it.

User impact

Hosts with working hardware rendering keep the existing fast path. In environments where hardware rendering is unavailable, emulator startup now recovers automatically using the current Android Emulator software-rendering mode.

Validation

  • bun run build
  • bun run typecheck
  • bun run lint
  • bun run test
  • focused fake-emulator test verifies the launch sequence is host followed by software

Co-authored-by: Codex <codex@openai.com>
krystofwoldrich and others added 4 commits August 18, 2026 13:44
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant